Download Administering Relational Databases on Microsoft Azure.DP-300.Dump4Pass.2022-01-08.177q.vcex

Reference: https://docs.microsoft.com/en-us/azure/dms/dms-overview 

Azure Database Migration service  Box 1: Premium 4-VCore Scenario: Migrate the SERVER1 databases to the Azure SQL Database platform. Minimize downtime during the migration of the SERVER1 databases.  Premimum 4-vCore is for large or business critical workloads. It supports online migrations, offline migrations, and faster migration speeds.  Incorrect Answers: The Standard pricing tier suits most small- to medium- business workloads, but it supports offline migration only.    Box 2: A VPN gateway YouneedtocreateaMicrosoftAzureVirtualNetworkfortheAzureDatabaseMigrationServicebyusingtheAzureResourceManagerdeploymentmodel,which provides site-to-site connectivity to your on-premises source servers by using either ExpressRoute orVPN.    Reference: https://azure.microsoft.com/pricing/details/database-migration/   https://docs.microsoft.com/en-us/azure/dms/tutorial-sql-server-azure-sql-onlinecorrected

Box 1: DTU Scenario: The 30 new databases must scale automatically.  Once all requirements are met, minimize costs whenever possible.    You can configure resources for the pool based either on the DTU-based purchasing model or the vCore-based purchasing model.  In short, for simplicity, the DTU model has an advantage. Plus, if you’re just getting started with Azure SQL Database, the DTU model offers more options at the lower end of performance, so you can get started at a lower price point than with vCore.   Box 2: An Azure SQL database elastic pool Azure SQL Database elastic pools are a simple, cost-effective solution for managing and scaling multiple databases that have varying and unpredictable usage demands. The databases in an elastic pool are on a single server and share a set number of resources at a set price. Elastic pools in Azure SQL Database enable SaaS developers to optimize the price performance for a group of databases within a prescribed budget while delivering performance elasticity for each database.    Reference: https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overview  https://docs.microsoft.com/en-us/azure/azure-sql/database/reserved-capacity-overviewconfirmed  

The lifecycle management policy lets you: Delete blobs, blob versions, and blob snapshots at the end of their lifecycles    Scenario: Purge Twitter feed data records that are older than two years.  Store Twitter feeds in Azure Storage by using Event Hubs Capture. The feeds will be converted into Parquet files.  Minimize administrative effort to maintain the Twitter feed data records.    Incorrect Answers: A: Time-based retention policy support: Users can set policies to store data for a specified interval. When a time-based retention policy is set, blobs can be created and read, but not modified or deleted. After the retention period has expired, blobs can be deleted but not overwritten.   Reference: https://docs.microsoft.com/en-us/azure/storage/blobs/storage-lifecycle-management-concepts

Scenario: Contoso requirements for the sales transaction dataset include: Implement a surrogate key to account for changes to the retail store addresses.    A surrogate key on a table is a column with a unique identifier for each row. The key is not generated from the table data. Data modelers like to create surrogate keysontheirtableswhentheydesigndatawarehousemodels.YoucanusetheIDENTITYpropertytoachievethisgoalsimplyandeffectivelywithoutaffectingload performance.    Reference: https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-identity

Box 1: Hash  Scenario: Ensure that queries joining and filtering sales transaction records based on product ID complete as quickly as possible. A hash distributed table can deliver the highest query performance for joins and aggregations on large tables.  Box 2: Round-robin Scenario: You plan to create a promotional table that will contain a promotion ID. The promotion ID will be associated to a specific product. The product will be identified by a product ID. The table will be approximately 5 GB.  A round-robin table is the most straightforward table to create and delivers fast performance when used as a staging table for loads. These are some scenarios where you should choose Round robin distribution: When you cannot identify a single key to distribute your data.  If your data doesn’t frequently join with data from other tables.  When there are no obvious keys to join.  Incorrect Answers: Replicated: Replicated tables eliminate the need to transfer data across compute nodes by replicating a full copy of the data of the specified table to each compute node. The best candidates for replicated tables are tables with sizes less than 2 GB compressed and small dimension tables.  Reference: https://rajanieshkaushikk.com/2020/09/09/how-to-choose-right-data-distribution-strategy-for-azure-synapse/ 

CE: Estimate the vCores needed for the pool as follows: For vCore-based purchasing model: MAX(<Total number of DBs X average vCore utilization per DB>, <Number of concurrently peaking DBs X Peak vCore utilization per DB)  A: Estimate the storage space needed for the pool by adding the number of bytes needed for all the databases in the pool. Reference: https://docs.microsoft.com/en-us/azure/azure-sql/database/elastic-pool-overviewconfirmed

Step 1: Attach the SSISDB database   Step 2: Turn on the TRUSTWORTHY property and the CLR property If you are restoring the SSISDB database to an SQL Server instance where the SSISDB catalog was never created, enable common language runtime (clr)    Step 3: Open the master key for the SSISDB database Restore the master key by this method if you have the original password that was used to create SSISDB.    open master key decryption by password = 'LS1Setup!' --'Password used when creating SSISDB'  Alter Master Key Add encryption by Service Master Key  Step 4: Encrypt a copy of the mater key by using the service master key Reference: https://docs.microsoft.com/en-us/sql/integration-services/backup-restore-and-move-the-ssis-catalog

Columnstore tables and indexes are always stored with columnstore compression. You can further reduce the size of columnstore data by configuring an additional compression called archival compression.    Note:Columnstore—Thecolumnstoreindexisalsologicallyorganizedasatablewithrowsandcolumns,butthedataisphysicallystoredinacolumn-wisedata format.   Incorrect Answers: B: Rowstore — The rowstore index is the traditional style that has been around since the initial release of SQL Server. For rowstore tables and indexes, use the data compression feature to help reduce the size of the database.  Reference: https://docs.microsoft.com/en-us/sql/relational-databases/data-compression/data-compression

This table lists the key features for PolyBase and the products in which they're available.           Incorrect Answers: C: Change tracking is a lightweight solution that provides an efficient change tracking mechanism for applications. It applies to both Azure SQL Database and SQL Server.    D: Azure SQL Database and Azure SQL Managed Instance automatic tuning provides peak performance and stable workloads through continuous performance tuning based on AI and machine learning.    Reference: https://docs.microsoft.com/en-us/sql/relational-databases/polybase/polybase-versioned-feature-summary